Checklist

General

• I tested all changes and their related features with all corresponding user types on a test server.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Server

• Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
• I followed the coding and design guidelines.
• I added multiple integration tests (Spring) related to the features (with a high test coverage).
• I documented the Java code using JavaDoc style.

Client

• Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
• I followed the coding and design guidelines.
• Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
• I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
• I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
• I documented the TypeScript code using JSDoc style.
• I added multiple screenshots/screencasts of my UI changes.
• I translated all newly inserted strings into English and German.

Changes affecting Programming Exercises

• I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
• I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).

Motivation and Context

Continuous plagiarism control (cpc) introduces possibility of a new approach for preventing plagiarism in student submissions. Cpc automatically scans all submissions and gently informs students, whose solutions are very similar to solutions of any other student.

Currently students receive information about a plagiarism case only after the exercise due date. This information itself has a form of punishment, as it leaves no room for improvement and can have severe consequences for the student. The new approach shortens the feedback loop of plagiarism checks and therefore encourages students to improve their solutions before the submission time is over. This may lead to less plagiarism cases opened for each exercises which improves the overall learning outcomes for students and reduces the amount of work to be performed by instructors.

Description

This is an experimental feature.

Continuous plagiarism control consist of the following features:

• plagiarism detection can start automatically each night during the submission period,
• optionally one more detection starts the night after the submission period is over,
• Artemis creates plagiarism cases for submissions included in plagiarism comparisons detected by the cpc,
• cpc plagiarism cases posts and notifications contain special messages that only mention possible similarities to other submissions (see screenshots for details)
• Artemis removes cpc plagiarism cases from submissions when any the subsequent cpc runs detects similarity is gone,
• Artemis stores configuration for cpc checks in the exercise model,
• instructors still can trigger manual plagiarism checks and configure them per run using the current interface.

When cpc detects plagiarism, authors of all plagiarism submissions will receive a plagiarism case and they will see a Significant Similarity button on the exercise participation site. This button is similar to the Plagiarism Case button visible when a standard plagiarism case is created for the exercise.

The cpc is an optional feature which needs to be explicitly enabled by the instructor. It may be necessary to verify the legal compliance before enabling it.

Steps for Testing

Prerequisites:

• 1 Instructor
• 2 Students
• 1 Programming, Text or Modelling Exercise
• test branch with cpc triggered every 1min deployed (plagiarism-detection-cpc-1min)

1. Deploy Artemis locally or on ts1.
2. Enable cpc for your exercise: set the cpc checkbox and a due data in the exercise creation page.
3. Create two identical submissions by two different students.
4. Wait 1min.
5. Verify that the notification about the plagiarism case was delivered to both students and that both students and the instructor can view it (see screenshots for reference).
6. Completely change one submission.
7. Wait 1min.
8. Verify that the plagiarism case was deleted.

Review Progress

Performance Review

• I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
• I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

Test Coverage

Screenshots

The Significant Similarity button visible on the participation page:

The cpc plagiarism case student notification:

The cpc plagiarism case student view:

The cpc plagiarism case instructor view:

The cpc plagiarism case email: